home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
comm
/
prom0406.zip
/
PROMENU.DOC
< prev
next >
Wrap
Text File
|
1990-04-06
|
36KB
|
1,083 lines
PROMENU 04/06/90 'Modern Protocol Manager` by Michael G Phelps
PROM0406.ZIP
SEE PRO_READ.1ST
ProMenu is simply a manager for some of the newer protocols, including
DSZ,BIMODEM,PUMA,LYNX,SUPERK,JMODEM.
Each protocol is equiped with two sets of "command lines to protocol".
Command lines to protocols are both viewable and editable from the
C)onfigure menu. PROMENU.CFG, initialy contains working default sets
for each protocol.
Protocols should be placed into a directory contained in your DOS PATH
statement. A DOS PATH statement is usualy contained, as one of the first
lines in the AUTOEXEC.BAT file.
EXAMLPE ==>> PATH=C:;C:\DOS;C:\TC;C:\EDITOR;C:\PROTS
Or,
If protocols are in a separate directory specified in the PROMENU.CFG
file, ProMenu will append your path statement with this directory.
Appended PATH statements last only while ProMenu is running.
My setup contains the protocol directory in PROMENU.CFG, and not in my
PATH statement.
SET PROMCFG=path ProMenu will use this directory for CFG file
set promcfg=c:\prots
This allows for a much cleaner setup, as Comm Program directories need not
be cluttered with all the protocols, and batch files assotiated with them.
ProMenu reads it's cfgfile for all protocols, and also the BIMODEM.CFG
file while in B)iModem part of ProMenu.
ProMenu will create it's cfgfile if none is found, in the current
directory. It checks CFG filesize, to see if it's a ok version.
Since ProMenu is a take off from the original BiMenu, I'l be refering to
B)imodem Menu from Prom., as Bimenu thruout most of this documentation.
Bimenu reads the BIMODEM.CFG file for filenames, directories, and port.
**>>BiMenu /BiHot, will use whatever PTH "filename" is contained in the
BIMODEM.CFG file. Allowing for multiples. Use C)onfig to change names.
I changed the TAG-BI to BIHOT for registered users of BIMODEM. Registration
is encouraged, as if for no other reason enables ALL BIMODEM features.
ProMenu's P)ut Pick function is many times faster, if your config.sys
contains:
files=20
buffers=10
This will allow your editors, directory listers etc. to run much faster,
than most DOS default settings.
PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
PROMxxxx.ZIP Was Zipped containing:
PROMENU.DOC
PRO_VERS.ION
PROMENU.EXE
BIHOT.EXE
Please do not add to or take from the above files package.
This includes Commpresion comments.
PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
________________Contents________________
ProMenu Pg's 1-4,10
1.........ProMenu.CFG
2.........CFG/Protocols
3.........Command Lines to Protocols
4.........Command Lines to Protocols
5.........Transfers
6.........PATH statements/ProMenu arguments
Bimodem/BiMenu Pg's 7 - 15
7.........Function Summary (short)
8.........BIHOT.EXE/P)ut-Pick
9.........BIMODEM.PTH / E)dit / D)elete
10.........S)tart / C)onfigure / Bimenu-use-files
11.........Installation - Configure Bimodem, Directory paths, Options
12.........Telix, Boyan - Installation examples
13.........Extended SetUp Help \
14.........Extended SetUp Help -- Bimodem
15.........Extended SetUp Help /
16.........Distribution
PROMENU -MODERN PROTOCOL SHELL Copyright 1989/1990 Michael G Phelps
_1_
ProMenu -Modern Protocol shell.
Basics...
===========
PROMENU.CFG
===========
The CFG file will be created with user input when ProMenu is invoked
and cannot locate it's CFG file in the current directory, or as set
with the DOS 'SET promcfg=c:\prots` command. Using "SET" will show
ProMenu a full pathname to it's CFG file.
Download path specified will be used for download activity.
ProMenu will change directories for download activity. Directory
specified in PROMENU.CFG will receive downloads. ProMenu changes back
when download activity is finished.
Upload path is the directory initialy listed by P)ut Pick.
Manual entries require a full pathname.
Uploads are presented to protocols with full pathname,
DRIVE\DIRECTORY\FILENAME.EXT . File names listed
in the batch window (uploads) are listed as filename only, full path
is contained in the list file.
PATHS are entered as: EXAMPLE==>> C:\BOYAN\DOWN
or: DOWN
Where down is a subdirectory of the current directory.
A "\" need not follow PATHS. ProMenu appends a "\" where needed, and
will strip a trailing "\" anyway.
Best to just enter DRIVE:\DIRCTORY format.
Your in the download directory during downloads, and the current directory
for uploads, except jmodem is in the upload directory.
ProMenu's M)anual option, accordingly, will expect a full path name.
SEE also the %PF switch;
Transfer protocol path will be appended to any existing PATH statement
found in the environment, or create a PATH, if non is found.
Environment changes will be restored to original when ProMenu exits.
ProMenu exits automaticaly after any transfer session.
LISTFILE is the filename that ProMenu stores uploads to, for use with
protocols with batch capability. Default is PROMENU.BCH
Port numbers are specified as "1" = "com1, "2" = "com2" etc., suports
com1 thru com4. ( For the send 'B CR` Bimodem to work corectly)
PROMENU -PROTOCOL shell Copyright 1989/90 Michael G Phelps
_2_
PROMENU.CFG -continued
Default protocol selection determines which menu will come up at
startup. This may be overriden with the [p] on commandline.
All CFG options may be changed/toggled from any menu with the C)onfig
option.
====================
INDIVIDUAL PROTOCOLS
====================
All protocols supported are available on the Key_Board. ProMenu will
use CFG information and invoke protocols with all needed information, first
changing directories (DownLoad), or supplying filenames (Upload). Batch
protocols will operate in Batch or Single-file mode. Protocols with
batch capability, always, are fed a list file, in the form:
@DRIVE:\DIR\LISTFILE
While ProMenu provides easier operation to some users for supported
protocols, It is recommended that those often used be registered.
I'm not going to go into explaining each protocol operation. Except
that PUMA has a PUMASETUP program, which writes terminal specific data
to the PUMA.EXE file. If you don't use COM1, you will at least have to
run the setup, and change comm ports.
Superk will need to know it's overlay path.
Bimodem needs to have it's own CFG file in order.
DSZ.COM/EXE
PUMA.EXE -- Full batch capability, crash recovery, or enable resume
LYNX.EXE
SUPERK.EXE
JMODEM.COM -- Single file (This is not the J found with SK package)
BIMODEM.COM -- Bidirectional, interupt recovery,refresh
PROMENU -PROTOCOL shell Copyright 1989/90 Michael G Phelps
_3_
==========================
Command Lines to Protocols
==========================
From the C)onfigure menu, will be displayed two sets of command-lines.
The T)oggle option, toggles which set is currently in use. Each
protocol has a "Default" set (Up/Dn), and a "Custom" set of command
lines to protocol. Editing the command sets, is possible with the E)dit
option from C)onfigure menu. Set in use is displayed next to the toggle
option. Command-line "Switch" symbols, and their meaning, are visible
in the lower box.
The following switches will take place, as represented on the command line
to protocol.
Switch symbals -meanings